… and sweeping

Acceptance tests name cloud resources with a bare random string
($UNIQUE_NAME, e.g. 'osr5mzrrvzb73juixjoviti24y'). When such resources
leak into shared test workspaces, nothing ties them back to a repo or CI
run, which made a recent quota-exhaustion incident hard to diagnose and
makes targeted cleanup impossible.

When running against a cloud env (CLOUD_ENV set) with GITHUB_RUN_ID
present, the harness now generates names of the form
'ci-<GITHUB_RUN_ID>-<random>', truncated to the same 26-character length
as before so that length-constrained names built from $UNIQUE_NAME
(e.g. 'app-$UNIQUE_NAME', exactly 30 chars, the app name limit) keep
fitting. The character set stays lowercase alphanumerics plus '-', which
tests already use adjacent to $UNIQUE_NAME in every resource type.
Local runs and testserver runs are unchanged, and output masking is
unaffected because the whole generated name (prefix included) is still
replaced with [UNIQUE_NAME].

Also adds tools/sweep_test_resources.py, a small helper that lists (and
with --delete removes) warehouses, pipelines and jobs whose names start
with a given prefix, to be wired into CI job-end cleanup later.

Co-authored-by: Isaac

Co-authored-by: Isaac

Drop the CLOUD_ENV gate: ciUniqueName already no-ops without a valid
run id, and prefixing testserver runs in CI exercises the masking path
everywhere instead of only on cloud runs.

Co-authored-by: Isaac

Python project_name validation rejects hyphens ("must consist of
letters, numbers, and underscores"). The CI run-id prefix
introduced by ciUniqueName uses hyphens (ci-<runID>-<random>),
causing bundle init to fail in the two default-python test
templates that embed $UNIQUE_NAME directly in project_name.

Fix: expose UNIQUE_NAME_SAFE (hyphens replaced with underscores)
alongside UNIQUE_NAME, add masking for it, and use it in the two
input.json.tmpl files and the integration_classic script.
Resources that accept hyphens (jobs, pipelines, apps, warehouses)
continue using the original $UNIQUE_NAME format.

Co-authored-by: Isaac

The previous ci-<runID>-<random> format injected hyphens into
$UNIQUE_NAME, which is embedded into ~hundreds of test resource
names. Hyphens are rejected by Python project names, Unity Catalog
identifiers, and vector-search index names, so local acceptance
jobs failed (e.g. bundle/templates/default-python and
bundle/deployment/bind/vector_search_index).

Switch the format to ci<runID>x<random>, which is purely
lowercase-alphanumeric like the base32 name it replaces and is
therefore valid in every naming context (including app names,
which forbid underscores and uppercase). The run id is delimited
from the random tail by the letter "x", keeping the sweep prefix
ci<runID>x collision-free. This needs no per-template changes, so
the UNIQUE_NAME_SAFE approach from the prior commit is reverted.

Co-authored-by: Isaac